Labels:text | screenshot | number | font | menu OCR: Feature Traditional MOM, RPC, and Conversations Transactional MOM, RPC, and Conversations Who participates? Loosely coupled client/server programs. Transactionally bound client/server and server/server programs. The message invocation causes the recipient program to join the transaction. Commit synchronization NO Yes Only-once semantics NO Yes Server management No. It's just a delivery mechanism. Yes. The process that receives the message is started, on the recipient node load-balanced, monitored, and tracked as part of the Transaction. Load balancing Uses the directory services. The first Uses the TP Monitor's sophisticated load-balancing server to register becomes a hot spot. algorithms. Can spread work across multiple SMP No dynamic load balancing is provided. machines and dynamically add more processes to cover hot spots of activity. Supervised exchanges No. Exchanges are simply between the client The TP Monitor supervises the entire exchange, restarts and the server. The exchanges are transient. communication links, redirects messages to an alternate No crash recovery or error management is server process if the first one gets hung, performs retries, provided, You're on your own. and provides persistent queues and crash recovery. TABLE 1. Traditional vs. transactional communications.
